Settings - Code Definition

(This functionality is available with the Input / Output module)

Sets the feature code definition structure.

Feature codes in RAW files and Field files will be interpreted according to the settings made in the Code Definition dialog box.

The feature code field may be defined to contain string identifiers as well as feature codes. It is imperative that the definition set here matches the actual code structure used in the field. Otherwise the codes will not be interpreted or strung as desired.

Code Definition

Code Definition dialog box

Item Used to
Code Size Set the number of characters in the feature code component.
The maximum number of characters in the feature code component is eight.
String Identifier Define the string identifier component.
Select the None, One Character, or Two Character radio buttons to define the size of the string identifier component. The string identifier is optional and will not be included in the code definition if the None button is selected.
Select the "String at end" check box to position the string identifier at the end of the feature code. Alternatively, the string identifier will be at the start.
Note also that if you are using Wildsoft field coding techniques, some of the Wildsoft operation codes may not be used if the code definition contains a string component. Refer to the Wildsoft Operation Codes topic.
Non Stringing Character: Set the character that is to be used in the string identifier component of the code field, to indicate that the point is not to be part of a string.
For example, if this character is 0 and the length of the string identifier component is two characters, then a point with a code field which has 00 as the string identifier would not be strung.
Current Setting Show the current setting for the code definition
"C" indicates a component of the feature code.
"S" indicates a component of the string identifier.
Treat Codes as Numeric: Select whether the codes are to be treated as numeric.
If this check box is active then the following will apply:
When a field file is created from the raw file using the Resolve/Create Field File command, the feature code field will be treated as left justified and any characters to the right of the overall code size will be ignored. For example, if the code setting was CCCSS, a code field of 123401 in the Raw file would the converted to 12340 in the Field file.
When the field file is reduced using the Resolve/Reduce Field File command, the feature code will be converted to a number for the purpose of locating the feature code in the code table used. For example, for the above settings, a code field of 00501 in the field file would be treated as a feature code of 5 and part of a string joining all points with the same code and string identifier of 01. The code table could therefore have a code of 5 or 005, as when in numeric mode, leading zeroes are ignored for comparison.
If this check box is not active then the following will apply:
When a field file is created from the raw file using the Resolve/Create Field File command, the feature code field will be treated as right justified and any characters to the left of the code size will be ignored. For example, for the above settings, a code field of 123401 in the Raw file would be converted to 23401 in the Field file.
When the field file is reduced using the Resolve/Reduce Field File command, the feature code will not be converted to a number for the purpose of locating the feature code in the code table used. For example, for the above settings, a code field of 00501 in the field file would be treated as a feature code of 005 and part of a string joining all points with the same code and string identifier of 01. The code table should therefore have a code of 005 defined, not 5.
Leica
Wildsoft Inform the system that the RAW file selected has been collected using Wildsoft field coding rather that this systems preferred field coding.
This check box will only have an effect if the RAW file was collected using Wild equipment.

If you are using Wild equipment, ensure that this check box is:
  • -checked if you used Wildsoft coding;
  • -not checked if you used this systems normal Wild coding.

Setting this incorrectly will produce unpredictable results.
If you are processing a Wild RAW file using Wildsoft coding, and more than one job exists in the RAW file, the system will display a list of the jobs in the RAW file enabling the required job to be selected.
Ignore Observations Inform the system to ignore any Leica/Wild Measurement Blocks that are recorded and to reduce the data using the recorded co-ordinate information blocks 81, 82 and 83.
Leica On-board Lines Inform the system that Leica On-board Line Features are to be included in the Raw file.
If you select this option, you should ensure that:
- the code definition string identifier (above) is set to zero
- the Reduction Options dialog has the "Use Code Table Stringing" option not selected to avoid unwanted strings being generated via the code table.
Traverse App as Rounds Treat Leica traverse app observations as rounds of directions.
Description Attribute Specify the name of the Leica DBX code list attribute which is to be regarded as a point/line/polygon description.
The point descriptions will use the Leica/Wild operation code 14. The line descriptions will use the Leica/Wild operation code 65, so will only work for lines if the Leica on-board lines box is checked, when the line work is processed. Note that if the Description checkbox is on, but the on board lines checkbox is not on, the point description processing is performed, but not line description processing
Set orientation kept on datum If checked setup orientation is assumed to be on datum if sighting back to a station whose coordinates are undefined.
If not checked, then the set orientation is assumed to not be on datum and may be rotated once the coordinates of the backsight station are known, or a reduction warning may occur if the backsight station remains unknown.
OK Save any change made to the settings and close the dialog box.
Cancel Close the dialog box without saving any changes.

The only exceptions to the stringing rules are that fixed coordinate points are never strung regardless of their feature codes. Such points appear in a field file as record types 061 to 065.

The sample codes shown in the dialog box above for that particular code definition will be interpreted as follows: